-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
perf: add parallelization #34
base: main
Are you sure you want to change the base?
Conversation
96868c0
to
0658cc6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The clippy settings and code cleanup are welcome additions, but the parallelization of tripsu index
degrades performance on my side (see comments).
@cmdoret , @supermaxiste : the |
fix: correct all clippy errors fix: add CLI argument to setup the thread pool fix: CLI handling fix: wrong argument docs(readme): add copyright notice (#35) fix: parallelize also second pass fix: correct output in `write` -> `write_all` - `write` may fail an return the number of bytes written, which is the wrong function. fix: remove from first-pass since no benefit
8c15fb0
to
51cd62f
Compare
@gabyx : This PR is draft, and should be revisited once parallelization is needed with longer work on the pseudonomization function |
Proposed Changes
Add parallelization over
rayon
which lets you convert an iterator to aParallelIterator
whichis parallelized over
rayon
's thread pool.Note:
rio
'sinto_iterator
is abit stupid written, dont see the intention to store a fullVec<T>
Add a CLI flag
--parallel
which will use parallelizationIf the parallelization pays out has yet to be tested. The
Mutex
on the Writer is not particularly good I guess. -> useslog
s async writter which is buffered and isSend + Sync
...Types of Changes
What types of changes does your code introduce? Put an
x
in the boxes thatapply
functionality to not work as expected).
other choices apply).
Checklist
Put an
x
in the boxes that apply. You can also fill these out after creatingthe PR. If you're unsure about any of them, don't hesitate to ask. We're here to
help! This is simply a reminder of what we are going to look for before merging
your code.
CONTRIBUTING
guidelines.
works.
Further Comments